May I add that it would be great if these plugins were to support custom registries right from the start.

For example, they could take a custom_registry keyword that would trigger the supplementation of the workflows:

• Add registry: user/CustomRegistry entry to TagBot.yml.
• Use CompatHelper.main(; registries=...) (see here for an example)

Assuming that custom_registry would take a URL to the registry the only not super straightforward part is that to do the latter we need the UUID information of the custom registry. But I guess we can just look it up in the Registry.toml file in the root of the registry repo.

Codecov Report

Merging #107 into master will increase coverage by 0.19%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #107      +/-   ##
==========================================
+ Coverage   91.84%   92.04%   +0.19%     
==========================================
  Files          15       17       +2     
  Lines         319      327       +8     
==========================================
+ Hits          293      301       +8     
  Misses         26       26

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a41187b...8389127. Read the comment docs.

I'm not going to do the CompatHelper one for now because it wouldn't have a very nice API (registries=[(name=..., uuid=..., url=...)] I guess), but I just pushed the TagBot changes I was sitting on.
The CompatHelper plugin does have a file option though, so you can just supply your own workflow file with any registries you need.

I'm not going to do the CompatHelper one for now because it wouldn't have a very nice API (registries=[(name=..., uuid=..., url=...)] I guess)

If we were to restrict ourselves to just a single custom repository I don't think the API would have to be like this. As I said above, we could use the same API as for TagBot: from "owner/registryrepo" we can generate the URL "http://github.com/owner/registryrepo/Registry.toml", where we find the name and uuid information of the custom registry.

Yeah I'm cool with that API. But since that requires HTTP, I'm going to wait on implementing it until we do more HTTP-related things (#79).

This is good to go, I'm just thinking about how I want to deal with JuliaRegistries/TagBot#36 (the TagBot template will change if I do the underscored inputs).

@christopher-dG Just FYI- I just registered CompatHelper version 1.0.0. It will be automerged within an hour.

Since the CompatHelper API is stable, how do you feel about it making it a default?

Yeah I'm cool with defaulting it, seems like it's been very well-received by the community.
Would love to see JuliaRegistries/CompatHelper.jl#123 released first though, since that makes the templating much easier and prettier 🙂

I'm gonna go ahead and merge this tonight (after I merge some stuff in TagBot). Custom registries are not supported in the default CompatHelper template, but you can bring your own if you need for now. Default support will come when CompatHelper has a nice config option for it.